Output Config Option Values in Canonical Case#58735
Output Config Option Values in Canonical Case#58735graphemecluster wants to merge 1 commit intomicrosoft:mainfrom
Conversation
typescript-bot
added
the
For Uncommitted Bug
|
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
|
For ecmascript versions I can sort of understand it, but I'm not totally convinced we consider "Node16" more canonical than "node16", "Preserve" etc, https://www.typescriptlang.org/tsconfig/#module And so on. |
|
I don’t know, I just completely sticked to the autocompletions provided by VSCode (except for a few subtle inconsistencies of |
|
The autocompletions in VS Code are just the ones from schemastore. Not sure any of us like those either 😄 |
|
Oh, I see. Wonder why we didn’t maintain one here or in the VSCode repo. |
3 participants
This aligns the letter cases of the values in
tsconfig.jsons generated bytsc --initand some diagnostics (e.g. TS1501, TS6046) with the autocomplete values provided totsconfig.jsonin VSCode and other diagnostics with hard-coded target versions.This should not affect anything related to value parsing.
Addresses #55600 (comment).